⚠️ No Changeset found

Latest commit: 79d1053

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Looks very, very good, but I fear that the goal of the examples is to have 100% parity with https://github.com/shadcn-ui/ui
It would probably be best to relocate this to a 'community shadcn-svelte examples repo', but I would like to know @huntabyte's opinion.

Looks very, very good, but I fear that the goal of the examples is to have 100% parity with shadcn-ui/ui It would probably be best to relocate this to a 'community shadcn-svelte examples repo', but I would like to know @huntabyte's opinion.

Hi, @leonardsimonse

A community shadcn-svelte examples repo sounds terrific. The other I was asking for help in Hunter's server how to create an animated mini drawer/sidebar, and I remember thinking to myself, if only we had a source/reference for complex stuff, but still relied on the raw Shadcn-svelte components and animations.

Question: where can we direct this conversation to and gather input? Because I'm all in on the examples repo idea, and willing to contribute a thing or two. 🙂

Question: where can we direct this conversation to and gather input? Because I'm all in on the examples repo idea, and willing to contribute a thing or two. 🙂

It doesn't necessarily have to live inside @huntabyte's organization, and I'd almost rather we get things started sooner than later :-) .

@shyakadavis, @leonardsimonse, @fernandolguevara, would either of you be willing to kick things off by creating a new repo to house community contributions?

I think there's a lot of inspiration to be had by looking at how the various "tailwind blocks" repos/sites are designed. The decisions we'd need to make upfront are the structure of the repo and contribution guidelines, obviously keeping the former as simple as possible (without being simplistic) and the latter as fair and inclusive as possible.

Of course, should @huntabyte want to create a shadn-svelte organization to house shadn-svelte and its associated repos, we could just keep the community contributions repo under there, which would increase visibility for as many users as possible vs users needing to discover it another way.

@huntabyte just made an organization svelte community, yesterday @stemcc

https://github.com/svecosystem